home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Toolkit for Duke Nukem 3D
/
Walnut Creek CDROM - Toolkit for Duke Nukem 3D.iso
/
rts
/
rtsfaq.txt
< prev
next >
Wrap
Text File
|
1996-07-22
|
17KB
|
381 lines
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
The Official RTS (Remote Ridicule Sound) FAQ ver 1.0
Written By: Charlie Wiederhold
Current as of: July 6th, 1996
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
CONTENTS:
<1> Introduction
<1.1> A word from the author
<1.2> About this FAQ
<1.2.1> Where to get this FAQ
<1.2.2> Revision history
<1.3> What is an RTS (Remote Ridicule Sound) file?
<1.3.1> Apogee and 3D Realms, just a little info
<1.3.2> Where RTS files come from
<1.3.3> Where RTS files can be used
<2> How to make an RTS file
<2.1> What you need to begin with
<2.2> Parameters for the sounds used
<2.3> How to make a script file
<2.4> I have this great file I made! What now?
<3> Decompiling RTS files
<3.1> What you need to begin with
<3.2> What to do with the RTS file
<4> Hints and suggestions for good RTS files
<4.1> What kinds of sounds should I use?
<4.2> About how long should they be?
<4.3> "I hate 8 bit sounds! I want 16 bit!"
<5> What files are already out there?
<5.1> How they are rated
<5.2> Front Ends for RTSMAKER.EXE
<6> Contacting People About RTS Files
<6.1> Charlie Wiederhold
<6.2> Apogee
<6.3> 3D Realms
<7> Credits
=============================================================================
The legal stuff that you probably won't read or even care about...
This FAQ is copyright (c) 1996 by Charlie Wiederhold. Nothing contained
within it may be distributed unless every single last ASCII character is
sent with it. I put them in there for a reason, so leave it. Thanks. All
credits shall be given to me, or to someone else by me. You may pirate this
copy as much as you want, cause if you paid for it, you really messed up.
All that I ask, is that you treat this with the proper respect in reverence
of the time I spent on it to help you. Thanks!
=============================================================================
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Section 1 - Introduction
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<1.1> A word from the author
I am a student at The University of Texas at Austin majoring in Computer
Science. I currently maintain the largest RTS archive in the world, located
at WiederWeb - http://ccwf.cc.utexas.edu/~wieder/ROTT/. I play lots of games,
and lots of game types, but 3D games tend to be my favorite. And, 3D
Realms/Apogee are my favorite gaming companies. I will explain that later.
Anyways, I CANNOT guarantee that everything within this FAQ is true. But,
I will try to be as correct as I can possibly be. If you notice an error,
or think something else should be in here, just contact me. I can be
contacted from my page, or you can just e-mail me at wieder@mail.utexas.edu
<1.2> About this FAQ
I wrote this thing to help people out who get a bit confused as to what an
RTS file is, and how to make them. Also, to attempt to bring to light, just
how cool these things are.
<1.2.1> Where to get this FAQ (and all subsequent updates)
WWW
http://ccwf.cc.utexas.edu/~wieder/ROTT
Usenet
alt.games.apogee
alt.games.duke3d
FTP
ftp://apogee.best.com
ftp://3drealms.best.com
You can also get it via e-mail by simply sending a bit of mail to
wieder@mail.utexas.edu, and asking for it.
<1.2.2> Revision history
Since this is the very first version, there is none.
<1.3> What is an RTS (Remote Ridicule Sound) file?
RTS (Remote Ridicule) files are the files that contain the sounds made when
you push <ALT><F1> through <ALT><F10> in Duke Nukem 3D and <F1> through <F10>
in Rise of the Triad. These first premiered in Rise of the Triad, and really
took off in popularity with the release of Duke Nukem 3D. I assume they will
continue to be used in many of Apogee's and 3D Realms' games. They are used
predominantly in Multi-playing as ways to express yourself about something
that happened, or is about to happen. The majority are humorous in nature,
but a few have ventured into making a serious file with a real purpose.
Please note: RTS files can be heard in both multiplay and single play in
Duke 3D. They can only be heard during multiplay in ROTT.
<1.3.1> Apogee and 3D Realms, just a little info
Apogee is the company that revolutionized the method of marketing games. They
released games as shareware before actually sending it to the selling blocks.
Now, almost all the major companies will release a shareware version of their
games before the actual full version. With such classics as Commander Keen,
Duke Nukem 1 & 2, the Kroz series, and many others, Apogee was able to
establish themselves as a major game maker. Some of the newer hits are Wacky
Wheels, Rise of the Triad, and Xenophage. With some new games in planning,
Apogee just keeps on going, providing some of the highest quality games out
there.
3D Realms is the fledgling branch of Apogee, that focuses on the 3D type
games. Currently they have released two games, Terminal Velocity, and the
smash hit Duke Nukem 3D. Look for many more fantastic 3D games from this
company, including Blood and Prey. Prey will be the first game to use the
TRUE 3D engine from 3D Realms.
<1.3.2> Where RTS files come from
RTS files originated with Rise of the Triad, and one came with the game. But,
Apogee gave out the program with which to create them, and now users have
taken over the spotlight. Over 100 new RTS files are now floating around the
internet, and I am sure that number will continue to grow as more users find
an interest in them.
<1.3.3> Where RTS files can be used
As stated before, RTS files can currently be used in two games. Rise of the
Triad, and Duke Nukem 3D. New RTS files can be selected for use in these
games from the setup programs. In Rise of the Triad, they are listed under
the "Use Modified Stuff" option, and in Duke Nukem 3D, they are changeable
from within the Modem, Serial, and Network options.
-----------------------------------------------------------------------------
----------------------------------------------------------------------------
Section 2 - How to make an RTS file
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<2.1> What you need to begin with
First of all, you need the program RTSMAKER.EXE. The most current is
RTSMaker v2.0. It allows you to not only assemble, but also take apart RTS
files. Very convenient when you have sounds from several RTS files that you
feel should be in one compact file. You can get this from almost any quality
Duke 3D or ROTT site (including the official 3D Realms and Apogee BBS web
pages), and also at my RTS web site. Plus, it is included with many titles
released by 3D Realms/Apogee. RTSMaker v1.0 is available from the ROTT CD,
and the disk based ROTT Power Pack. RTSMaker v2.0 is available on the Duke3D
CD.
Before you do anything, you may want to check out one of the deepest secrets
of the RTSMAKER.EXE file. Just type it at the DOS prompt, and some wonderful
help information comes up. Believe me, very few people even know about it.
You will need 10 .WAV or .VOC sound files. Many cool sound files can be
found around the internet, or maybe you have some on your computer. If you
like a certain theme look for a web site about that theme, and you are almost
guaranteed to find some cool .WAV files there. You can use both .VOC and .WAV
files when creating an RTS file.
Also, there are many .WAV and .VOC file editors out there, one of which is
currently at my web site. You can visit several sound related web sites and
find some other good editors. These can be used to clean up a sound, or cut a
sound to make it shorter.
But, the basics are RTSMAKER.EXE and 10 .WAV or .VOC sound files.
<2.2> Parameters for the sounds used
I do not currently know the variations of sounds that can be used to create
an RTS file, but please keep in mind that you should keep them fairly simple.
Here are a few notes from Mark Dochtermann:
You can have 8 or 16 bit sounds.
You CANNOT have stereo.
You can have anywhere from 2Khz to 44Khz sounds.
The size of a sounds is not limited, but the game has to be able to load it.
You make it too big, and the game may crash trying to play it. Trust me, the
simpler they are... the more effective in game play they seem to be.
A neat trick that has never before been released until now (Thanks Jim Dose!),
is that you can make an infinite RTS sound. If you construct your .WAV or
.VOC in such a way that it loops, you can put THAT in the RTS file. Then, when
the person goes to select that sound, it will keep playing on forever. Not
a very FUN trick for everyone else playing the game, but hey... it is still
a trick! Don't go asking me for help on how to make a looping sound file...
I don't have a clue, and will not learn how just so I don't ever have to
tell anyone. ;^)
<2.3> How to make a script file
In order to make a script file, you need to know the format for what
RTSMAKER.EXE will look for. Just use any ASCII editor (ex. DOS Edit) just
as long as it saves the file in raw ASCII text.
Now, on the first line of this file, type the name of the RTS you want it to
make. This is so RTSMAKER.EXE will know what to call the file it is going to
create. Then, on each line after that, type the names of the sound files you
want included. Be sure to type the whole thing, including the extension.
When you are done, save the file. Then, make sure that RTSMAKER.EXE, your
script file, and the sound files are all in the same directory. Now, all you
have to do is type RTSMAKER <Name of your script file here> at the command
prompt, and it will compile it and save the new RTS as whatever you specified
in the script file.
So, here is an example of a script file named MAKERTS.TXT that I might use.
MyRTS.RTS
Sound1.WAV
Sound2.VOC
Sound3.WAV
Sound4.WAV
Sound5.WAV
Sound6.VOC
Sound7.WAV
Sound8.WAV
Sound9.VOC
Sound10.WAV
Then, after I saved this text file as MAKERTS.TXT, I would type this at the
command prompt:
rtsmaker makerts.txt
Note: It is often convenient to rename the sounds you want to something
simple to remember, like Sound<#>.(WAV/VOC). This is for your sake to help
prevent typos when trying to remember the names of all the sound files.
<2.4> I have this great file I made! What now?
You can upload this to me by sending it via e-mail to wieder@mail.utexas.edu
I post every RTS file I get, unless of course, it doesn't work. This is the
suggested way, because pretty much all other Duke or ROTT sites get their
RTS files by checking in on my site. Thus, you have a higher chance of more
people seeing it by sending it to me. Also, you will be ensured to get the
proper credit. The only people who do not receive credit are people who send
their file elsewhere, and the maintainer doesn't bother to say who made it.
But, if you have a favorite site, go ahead and upload it to them. Chances
are, I will find it anyways and have it posted soon enough. :^)
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Section 3 - Decompiling RTS files
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<3.1> What you need to begin with
You must have RTSMaker v2.0 in order to decompile an RTS file.
<3.2> What to do with the RTS file
Type RTSMAKER -u <Name of RTS>.RTS at the command prompt.
For example: rtsmaker -u duke.rts
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Section 4 - Hints and suggestions for good RTS files
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<4.1> What kinds of sounds should I use?
You really should use sounds that fit into a theme. Of course, there are
many RTS files out there that are pretty random, and still funny or
effective, the best continue to be ones with a theme. As far as subject
matter, the sky is the limit... or should I say, the number of sounds in the
world is the limit?
<4.2> About how long should they be?
Long sounds tend to slow the game down while they are loading, and actually
get in the way. Also, they simply make the file pretty dang large, thus they
take a while to download and take up a lot of space. Short simple quotes that
quickly make their statement seem to have the most effect while multi-playing.
<4.3> "I hate 8 bit sounds! I want 16 bit!"
What quality of sound you pick is up to you. There are advantages either way.
8 bit sounds are naturally smaller, but do not have the clarity of a 16 bit
sound. You make the judgment yourself. Size or quality.
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Section 5 - What files are already out there?
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<5.1> How they are rated
I set the standard for rating them by placing them into a G and PG rated
section and a PG-13 and R rated section. Clarifying much more than that is
next to impossible. Basically, they are divided into ones that curse, and
ones that don't. Believe it or not, the number of G and PG rated ones out
number the PG-13 and R rated. Proving that you don't have to be vulgar to
be funny!
If you don't know what G, PG, PG-13, and R mean, just remember this:
G and PG are the family types, with no cursing or adult subject matter.
PG-13 and R have cursing and/or adult subject matter.
If you think a file belongs in a different category than what I have it
listed, just e-mail me and tell me. I will then re-evaluate it and see what
I think.
<5.2> Front Ends for RTSMAKER.EXE
There are currently two front ends for making RTS files. These programs
don't actually create the RTS, but make the process of selecting what you
want easier. These are:
WinRTS.zip - Windows based front end
MakeRTS.zip - DOS based front end written by yours truly
I will not provide much info about them, as they already have included
documentation.
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Section 6 - Contacting People About RTS Files
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
<6.1> Charlie Wiederhold
As stated before, I can be contacted via my web page at
http://ccwf.cc.utexas.edu/~wieder/ROTT/
Or, e-mail - wieder@mail.utexas.edu
<6.2> Apogee
WWW - http://www.apogee1.com/
e-mail - apogee.software@apogee1.com
<6.3> 3D Realms
WWW - http://www.3drealms.com/
e-mail - 3drealms@3drealms.com
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Section 7 - Credits
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
First of all, I would like to thank Joe Siegler for checking this for
errors, and being a big help in many aspects of my work I have done in
relation to Apogee and 3D Realms.
Plus, Mark Dochtermann and Jim Dose who verified a ton of information, as
well as implementing the idea of RTS files in the first place!
Dryden for sparking my interest in making a web site for Rise of the Triad,
which let to a Duke Nukem page, which is where I began to set the standard
for RTS files. Also, for all his help in teaching me much of what I know.